Claiming data from a virtual whiteboard

ABSTRACT

A method of storing data from a whiteboard application executed on a computing system including an interactive display device is provided. The method comprises storing, in a memory of the computing system, whiteboard data input to the whiteboard application in response to user interaction with the interactive display device, displaying a login selector on the interactive display device, upon detecting actuation of the login selector, identifying the user based on credentials of the user; and in response to identifying the user, (i) retrieving previews of stored whiteboard files from a user account in a cloud-based storage system corresponding to the identity of the user, (ii) displaying the previews on the interactive display device, and (iii) uploading the whiteboard data as a whiteboard file from the memory of the computing system to the user account.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation from U.S. application Ser. No.14/516,497, filed on Oct. 16, 2014, which claims priority to U.S.Provisional Patent Application No. 61/996,781, entitled “CLAIMING DATAFROM A VIRTUAL WHITEBOARD” filed on May 14, 2014, the entire disclosuresof each of which are herein incorporated by reference.

BACKGROUND

Prior whiteboard applications have been used via computer systems,enabling displayed content to be drawn upon or otherwise manipulated viainput devices such as mice, trackpads, touchscreens, etc. In this way,the whiteboard application can provide the functionality of a physicaldry-erase or chalkboard in a computing context. Whiteboard applicationsare commonly used in collaborative settings such as meetings,brainstorming sessions, classrooms, etc. Therefore, in some instances aplurality of users may manipulate content presented via the whiteboardapplication in one or more sessions. The data associated with themanipulation of the content may be saved locally by the computingsystem. However, the computing system using the whiteboard applicationmay be used by a number of users. Therefore, storing the data locallymay create security concerns. Furthermore, storing the data locally mayincrease the amount of storage needed in the computing system.Therefore, offloading the content may be desirable to alleviate thesecurity concerns and decrease local storage needs. However, offloadingthe content to a portable storage device (e.g., thumbdrive), forexample, can be cumbersome and require many awkward steps involvingnumerous input commands. Consequently, it may be inefficient for one ormore users to offload the content quickly during a collaborativesession. As a result, users may find interaction with the whiteboardapplication slow and awkward. Moreover, it may be difficult to uploadthe offloaded content for use in a subsequent whiteboard session,leading to additional interactive inefficiency.

SUMMARY

A method of storing data from a whiteboard application executed on acomputing system including an interactive display device is provided.The method comprises storing, in a memory of the computing system,whiteboard data input to the whiteboard application in response to userinteraction with the interactive display device, displaying a loginselector on the interactive display device, upon detecting actuation ofthe login selector, identifying the user based on credentials of theuser; and in response to identifying the user, (i) retrieving previewsof stored whiteboard files from a user account in a cloud-based storagesystem corresponding to the identity of the user, (ii) displaying thepreviews on the interactive display device, and (iii) uploading thewhiteboard data as a whiteboard file from the memory of the computingsystem to the user account.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to implementations that solveany or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a computing system configured to store data from awhiteboard application executed on the computing system.

FIG. 1B depicts the computing system of FIG. 1A further configured todisplay a login selector on an interactive display device.

FIG. 1C depicts the computing system of FIG. 1A further configured toidentify the user via a sign in prompt requesting the user enter a userID and a password.

FIG. 1D depicts the computing system if FIG. 1A further configured toaccess a user account on a cloud-based storage system.

FIG. 2A depicts the computing system of FIGS. 1A-1D further configuredto display a logout selector on the interactive display device.

FIG. 2B depicts the operation of the logout selector of FIG. 2A.

FIG. 3A depicts the computing system of FIGS. 1A-1D further configuredto retrieve previews of stored whiteboard files from the user account onthe cloud-based storage system.

FIG. 3B depicts the computing system of FIG. 3A configured to display astored whiteboard file corresponding to a selected preview.

FIG. 4 depicts the computing system of FIGS. 1A-1D further configured tocreate virtual sticky-notes and recognize privacy keywords viahandwriting recognition.

FIGS. 5A and 5B depict a flowchart for a method for storing data from awhiteboard application executed on the computing system in accordancewith an embodiment of the present disclosure.

FIG. 6 schematically depicts a non-limiting embodiment of a computingsystem in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

A whiteboard application executed by a computing system including aninteractive display device is described herein. The whiteboardapplication is configured to quickly and efficiently upload and downloaddata to and from a cloud-based storage device during a whiteboardapplication user session. Specifically, data may be generated via thewhiteboard application and subsequently sent to a cloud-based storagesystem when a user provides credentials to a user account in thecloud-based storage system. Additionally, previews of files stored inthe cloud-based storage device can also be presented via the interactivedisplay device in response to the user entering user credentials. As aresult, a user can not only easily offload desired content to acloud-based storage system but also quickly preview content stored inthe cloud-based storage system, thereby enhancing the current whiteboardsession. In this way, a user can quickly capture content and send thecaptured content to a cloud-based system for later use as well aspreview previously captured content stored in the cloud-based system.

FIG. 1A depicts a computing system 10 configured to store data from awhiteboard application 18 executed on the computing system 10. Thecomputing system 10 may be configured to include an interactive displaydevice 12 (e.g., interactive touch sensitive display device) and amemory 14 including instructions executable by a processor 15. Thewhiteboard application 18 may be stored in memory 14 as instructionsexecutable by the processor 15. The computing system 10 may be furtherconfigured to record, in the memory 14, a whiteboard file 24. Thewhiteboard file 24 may include whiteboard data 16 input into thewhiteboard application 18 by a user 20 via the interactive displaydevice 12.

The interactive display device 12 may include a sensing device 80. Thesensing device may include one or more of a capacitive touch sensor, anoptical touch sensor, etc. The interactive display device 12 may includea liquid crystal display (LCD), an organic light-emitting diode (OLED),active-matrix organic light-emitting diode (AMOLED), projection display,etc., for presenting graphics. The interactive display device 12 isconfigured to receive and process ink inputs and touch inputs. It willbe appreciated that an ink input includes an interactive input with astylus 82. The interactive display device 12 may further be configuredto receive and process multi-touch inputs. Additionally, it will beappreciated that the aforementioned inputs may be sent to the memory 14and processor 15 for processing via the whiteboard application 18.

FIG. 1B depicts the computing system 10 further configured to display alogin selector 26 on the interactive display device 12. The loginselector 26 may be a soft button generated graphically by theinteractive display device 12 or a hard button physically present on theinteractive display device 12, itself. Upon detecting actuation of thelogin selector 26, the computing system 10 may then be furtherconfigured to identify the user 20 based on credentials of the user 20.In one example, the login selector 26 may be a soft button persistentlydisplayed on the interactive display device 12 via the whiteboardapplication 18. In this way, a user can quickly select the loginselector while the whiteboard application is executed. However, otherwhiteboard application user interface configurations have beencontemplated, such as using biometric indicators including facial imagerecognition to log a user in, or using a device identifier received froma user device (e.g., mobile phone, watch, stylus, etc.) to log a userin, as described below.

FIG. 1C depicts the computing system 10 further configured to identifythe user 20 via a sign in prompt 28 requesting the user 20 enter a userID 30 and a password 32. The user 20 is identified by the computingsystem 10 as “USER A”. The computing system 10 may also be furtherconfigured to identify the credentials of the user 20 via facialrecognition. For example, the computing system 10 may be configured tocompare a captured image of the user 20 captured with camera 40 to astored profile image associated with a cloud-based account (e.g., onlineaccount) of the user 20. The camera 40 linked to the computing system10. In addition, the computing system 10 may be configured to identifythe user 20 by wirelessly detecting the credentials of the user storedin a linked portable device. In FIG. 1C, the linked portable device isdepicted as cell phone 42 which may be configured to communicatewirelessly with the computing system 10. It should be noted, however,that the computing system 10 may be configured to wirelessly detect thecredentials of a user 20 via another suitable device, such as a securitytoken (e.g., fob), stylus, or watch.

FIG. 1D depicts the computing system 10 further configured to access auser account 34 on a cloud-based storage system 36. The user account 34corresponds to the identity of the user 20 established by the computingsystem 10, as described above with respect to FIG. 1C. Upon accessingthe user account 34, the computing system 10 may be configured to uploadthe whiteboard file 24 from the memory 14 of the computing system 10 tothe user account 34. For example, the computing system may be configuredto display on the interactive display device 12 a save selector 62 and,upon detecting actuation of the save selector 62 by the user 20, toupload the whiteboard file 24 to the user account 34.

Turning briefly to FIG. 2A, the computing system 10 may be furtherconfigured to display a logout selector 38 on the interactive displaydevice. As shown in FIG. 2B, the computing system 10 may be thenconfigured to revoke access to the user account 34 upon detectingactuation of the logout selector 38 by the user 20. Additionally,previews of the files stored in the cloud-based storage system may beremoved from the interactive display device upon detecting actuation ofthe logout selector. The previews are discussed in greater detailherein.

Turning next to FIG. 3A, the computing system 10 may be furtherconfigured to retrieve previews 44 of stored whiteboard files 46 fromthe user account 34 on the cloud-based storage system 36. For example,the computing system 10 may be configured to display an open selector 64on the interactive display device 12 and, upon detecting actuation ofthe open selector 64 by the user 20, to retrieve previews 44 of thestored whiteboard files 46 from the user account 34. The computingsystem may then be configured to display the previews 44 on theinteractive display device 12. The previews 44 may be displayed by thecomputing device as a horizontal strip of preview images, with thepreview images grouped chronologically. The previews 44 may be furthergrouped into folders. Additionally or alternatively, the previews may bepresented as tiles (e.g., tiles aligned in a grid pattern) or stackedwith each preview having a different z-order. The computing system 10may be further configured to allow the user 20 to select one of thepreviews 44 via the interactive display device 12. Upon detecting aselection by the user 20, the computing system 10 may be configured toretrieve the stored whiteboard file 46 corresponding to the selectedpreview 44. As shown in FIG. 3B, the computing system 10 may then beconfigured to display the stored whiteboard file 46 on the interactivedisplay device 12. The whiteboard application may be configured toenable the user manipulate the whiteboard file, such as addingadditional content, erasing content, modifying content, etc. Forinstance, a user may implement an ink input and/or touch input togenerate additional graphics (e.g., alphanumeric symbols) in thewhiteboard file.

Turning back to FIG. 1D, the computing system 10 may be furtherconfigured to display a second login selector 50 on the interactivedisplay device 12. The computing system 10 may be configured to identifya second user 52 based on credentials of the second user 52 afterdetecting actuation of the second login selector 50 by the second user52. The computing system 10 may then be configured to access a seconduser account on a cloud-based storage system corresponding to theidentity of the second user 52 and upload the whiteboard file 24 fromthe memory 14 of the computing system 10 to the second user account.Although only the user account 34 is depicted in FIG. 1D, it should benoted that the computing system 10 may be configured to upload thewhiteboard file 24 from the memory 14 to the second user account, aswell. For example, it should be further noted that the computing system10 may be configured to allow multiple user to operate in a split-screenmode wherein the whiteboard data from one predetermined half of theinteractive display device is uploaded to the user account of the firstuser, and the whiteboard data from the other half may be uploaded to theuser account of the second user. In another example, multiple users maybe able to select portions of the whiteboard data and upload only theselected portion to their user account.

Turning next to FIG. 4, the computing system 10 may be configured tocreate virtual sticky-notes 54 via the interactive display device 12.The virtual sticky-notes 54 may contain content such as text input bythe user and may be associated with a location or an element in thewhiteboard data. For example, if a virtual sticky-note 54 is placed on alocation within the whiteboard data of the whiteboard application 18,the virtual sticky-note 54 will remain in that location even if thewhiteboard data is scrolled or resized on the interactive display device12. The virtual sticky-notes 54 may also be configured such thatmultiple virtual sticky-notes may be stacked, resized, or arranged onthe screen by the user 20. The computing system 10 may be furtherconfigured to record the virtual sticky-notes 54 in the memory 14 and toupload the virtual sticky-notes 54 to the user account 34 as a part of awhiteboard file 56. As such, the virtual sticky-notes can be stored onthe computing system 10 and in user account 34 of the user 20.

FIG. 4 further depicts the computing system 10 configured to detect aprivacy keyword 58 via handwriting recognition on the interactivedisplay device 12. In the example shown in FIG. 4, the computing system10 is configured to detect the word “Secret” or another suitable privacykeyword, such as confidential, private, etc., via handwritingrecognition. The computing system 10 may then be configured to assign aprivacy level 60 to the whiteboard file 56 based on the privacy keyword58. The computing system may then be configured to restrict access tothe whiteboard file 56 based on the privacy level 60. For example, thecomputing system 10 may be configured to restrict access to thewhiteboard file 56 by locking the file and not allowing any unauthorizedusers to upload the whiteboard file 56. Alternately, the computingsystem 10 may be configured to restrict access to a whiteboard file 56by not displaying a preview of the file among the previews of storedfiles retrieved from the user account 34 if unauthorized users arecurrently logged into the computing system 10. In another example, thecomputing system 10 may restrict access to a whiteboard file 56 bydisplaying a warning message when an additional user logs into thecomputing system 10, if the additional user is not authorized to uploadthe whiteboard file 56.

FIG. 5 is a flowchart depicting a method 500 of storing data from awhiteboard application executed on a computing system including aninteractive display device. At 502, the method 500 includes receivingink inputs and/or touch inputs at the interactive display device. Itwill be appreciated that the ink inputs may be implemented via a stylusand the touch inputs may be implemented via digits of a user, forinstance.

Next at 504 the method includes generating whiteboard data based on thereceived inputs in response to receiving the inputs. In one example, thewhiteboard data is in a data format specific to the whiteboardapplication. However, other whiteboard data formats have beencontemplated. Further in one example, the whiteboard data includes atleast one of modifiable ink input data, touch input data, andsticky-note data associated with a location or another element in thewhiteboard data. It will be appreciated that the sticky-note data maymimic the functionality of physical sticky notes on a physicalwhiteboard.

At 506 the method includes storing, in a memory of the computing system,the whiteboard data in response to receiving the inputs at theinteractive display. In one example, the whiteboard data may be storedin the memory in direct response to receiving the inputs at theinteractive display. In the context of the invention direct responsemeans that there are not intervening input commands implemented betweenthe corresponding actions. Next at 508 the method includes detecting aprivacy keyword via handwriting recognition on the interactive displaydevice and at 510 the method includes assigning a privacy level to thewhiteboard data based on the privacy keyword. The privacy keyword may be“secret”, “classified”, “confidential”, etc. At 512 the method includesrestricting access to the whiteboard data based on the privacy level. Inthis way, a user may provide increased security to data quickly andintuitively through interaction with the interactive display device.

At 514 the method includes displaying a login selector on theinteractive display and at 516 the method includes detecting actuationof the login selector. Detecting actuation of the login selector mayinclude detecting actuation of a button via user input (e.g., ink input,touch input, mouse input, etc.), for instance. At 518 the methodincludes upon detecting actuation of the login selector, identifying auser based on credentials of the user. Identifying the user based on thecredential of the user may include at 520 prompting user to input ausername and password associated with a user account on a cloud-basedstorage system. Additionally or alternatively, identifying the userbased on the credentials of the user may include at 522 determining theidentity of the user based on a facial recognition. Additionally oralternatively, identifying the user based on the credential of the usermay include at 524 wirelessly detecting the credentials of the userstored in a linked portable device and at 526 determining the identityof the user based on the credentials. In one example, the linkedportable device is one of a stylus, mobile computing device, andsecurity token device. Thus, the credentials may be supplied by at leastone of a stylus, mobile computing device, and security token device viawireless communication. In this way, a device associated with the usermay be used to quickly identify the identity of the user.

Now turning to FIG. 5B, the method includes at 528-534 in response toidentifying the user (i) retrieving preview of stored whiteboard filesfrom a user account in a cloud-based storage system corresponding to theidentity of the user, (ii) displaying the previews on the interactivedisplay device, and (iii) uploading the whiteboard data as a whiteboardfile from the memory of the computing system to the user account. Inthis way, whiteboard data may be quickly pushed and pulled from the useraccount in the cloud-based storage system. In one example, the uploadedwhiteboard data only includes a selected portion of data presented onthe interactive touch sensitive display associated with the whiteboardapplication. For instance, a user may select a portion of the data viaan ink input, touch gesture, etc., indicating the portion of data theywould like to be uploaded. Still further in other examples, a stylus maybe associated with a user and only the portion of whiteboard datagenerated by the specific stylus may be uploaded to the cloud-basedstorage system. However, in other examples all of the whiteboard datapresented on the interactive display may be uploaded to the cloud-basedstorage system.

At 536 the method includes receiving a selection input of one of thepreviews via the interactive display device. Next at 538 the methodincludes retrieving the stored whiteboard file corresponding to theselected preview from the cloud-based storage system. At 540 the methodincludes displaying the stored whiteboard file on the interactivedisplay and at 542 the method includes displaying a second loginselector on the interactive display. At 544 the method includesdetecting actuation of the second login selector. At 546 the methodincludes upon detection of actuation of the second login selector,identifying a second user based on credentials of the second user. Nextat 548 the method includes in response to identifying the second user,uploading the whiteboard data from the memory of the computing system toa second user account in the cloud-based storage system, the second useraccount distinct from the first user account. At 550 the method includesdisplaying a logout selector on the interactive display device. Next at552 the method includes upon detecting actuation of the logout selector,revoking access to the user account and removing the previews of thestored whiteboard files from the interactive display device.

The above described systems and methods provide the potential advantagethat a user can quickly pull and push data to and from a cloud-basedstorage system. As a result, the users can quickly and intuitivelyacquire relevant data during a collaborative session for use at a latertime. Furthermore, previously stored files are presented during thecurrent whiteboard session for use during the current whiteboardsession, if desired, further expanding the content that can be used is asingle session. In this way, data from multiple whiteboard sessions canbe provided in a single interface further enhancing the currentwhiteboard session by providing greater amount of collaborative content.As a result, the functionality of the whiteboard is expanded to providea user with quick and efficient access to cloud-based content. In thisway, content from more than one whiteboard session may be linked via acloud-based storage system enabling the user to link content frommultiple whiteboard sessions, if desired.

In some embodiments, the methods and processes described herein may betied to a computing system of one or more computing devices. Inparticular, such methods and processes may be implemented as acomputer-application program or service, an application-programminginterface (API), a library, and/or other computer-program product.Specifically, the methods and processing herein may be tied to thecomputing system discussed above with regard to FIGS. 1-4.

FIG. 6 schematically shows a non-limiting embodiment of a computingsystem 600 that can enact one or more of the methods and processesdescribed above. Computing system 600 is shown in simplified form.Computing system 600 may take the form of a touch-screen display device,as well as any other suitable computing system, including but notlimited to game consoles, one or more personal computers, servercomputers, tablet computers, home-entertainment computers, networkcomputing devices, gaming devices, mobile computing devices, mobilecommunication devices (e.g., smart phone), and/or other computingdevices.

Computing system 600 includes a logic machine 602 and a storage machine604. Computing system 600 may also include a display subsystem 606,input subsystem 608, communication subsystem 610, and/or othercomponents not shown in FIG. 6.

Logic machine 602 includes one or more physical devices configured toexecute instructions. For example, the logic machine may be configuredto execute instructions that are part of one or more applications,services, programs, routines, libraries, objects, components, datastructures, or other logical constructs. Such instructions may beimplemented to perform a task, implement a data type, transform thestate of one or more components, achieve a technical effect, orotherwise arrive at a desired result.

The logic machine may include one or more processors configured toexecute software instructions. Additionally or alternatively, the logicmachine may include one or more hardware or firmware logic machinesconfigured to execute hardware or firmware instructions. Processors ofthe logic machine may be single-core or multi-core, and the instructionsexecuted thereon may be configured for sequential, parallel, and/ordistributed processing. Individual components of the logic machineoptionally may be distributed among two or more separate devices, whichmay be remotely located and/or configured for coordinated processing.Aspects of the logic machine may be virtualized and executed by remotelyaccessible, networked computing devices configured in a cloud-computingconfiguration.

Storage machine 604 includes one or more physical devices configured tohold instructions executable by the logic machine to implement themethods and processes described herein. When such methods and processesare implemented, the state of storage machine 604 may betransformed—e.g., to hold different data.

Storage machine 604 may include removable and/or built-in devices.Storage machine 604 may include optical memory (e.g., CD, DVD, HD-DVD,Blu-Ray Disc, etc.), semiconductor memory (e.g., RAM, EPROM, EEPROM,etc.), and/or magnetic memory (e.g., hard-disk drive, floppy-disk drive,tape drive, MRAM, etc.), among others. Storage machine 604 may includevolatile, nonvolatile, dynamic, static, read/write, read-only,random-access, sequential-access, location-addressable,file-addressable, and/or content-addressable devices.

It will be appreciated that storage machine 604 includes one or morephysical devices. However, aspects of the instructions described hereinalternatively may be propagated by a communication medium (e.g., anelectromagnetic signal, an optical signal, etc.) that is not held by aphysical device for a finite duration.

Aspects of logic machine 602 and storage machine 604 may be integratedtogether into one or more hardware-logic components. Such hardware-logiccomponents may include field-programmable gate arrays (FPGAs), program-and application-specific integrated circuits (PASIC/ASICs), program- andapplication-specific standard products (PSSP/ASSPs), system-on-a-chip(SOC), and complex programmable logic devices (CPLDs), for example.

The terms “module,” “program,” and “engine” may be used to describe anaspect of computing system 600 implemented to perform a particularfunction. In some cases, a module, program, or engine may beinstantiated via logic machine 602 executing instructions held bystorage machine 604. It will be understood that different modules,programs, and/or engines may be instantiated from the same application,service, code block, object, library, routine, API, function, etc.Likewise, the same module, program, and/or engine may be instantiated bydifferent applications, services, code blocks, objects, routines, APIs,functions, etc. The terms “module,” “program,” and “engine” mayencompass individual or groups of executable files, data files,libraries, drivers, scripts, database records, etc.

When included, display subsystem 606 may be used to present a visualrepresentation of data held by storage machine 604. This visualrepresentation may take the form of a graphical user interface (GUI). Asthe herein described methods and processes change the data held by thestorage machine, and thus transform the state of the storage machine,the state of display subsystem 606 may likewise be transformed tovisually represent changes in the underlying data. Display subsystem 606may include one or more display devices utilizing virtually any type oftechnology. Such display devices may be combined with logic machine 602and/or storage machine 604 in a shared enclosure, or such displaydevices may be peripheral display devices.

When included, input subsystem 608 may comprise or interface with one ormore user-input devices such as a keyboard, mouse, touch screen, or gamecontroller. In some embodiments, the input subsystem may comprise orinterface with selected natural user input (NUI) componentry. Suchcomponentry may be integrated or peripheral, and the transduction and/orprocessing of input actions may be handled on- or off-board. Example NUIcomponentry may include a microphone for speech and/or voicerecognition; an infrared, color, stereoscopic, and/or depth camera formachine vision and/or gesture recognition; a head tracker, eye tracker,accelerometer, and/or gyroscope for motion detection and/or intentrecognition; as well as electric-field sensing componentry for assessingbrain activity.

When included, communication subsystem 610 may be configured tocommunicatively couple computing system 600 with one or more othercomputing devices. Communication subsystem 610 may include wired and/orwireless communication devices compatible with one or more differentcommunication protocols. As non-limiting examples, the communicationsubsystem may be configured for communication via a wireless telephonenetwork, or a wired or wireless local- or wide-area network. In someembodiments, the communication subsystem may allow computing system 600to send and/or receive messages to and/or from other devices via anetwork such as the Internet.

It will be understood that the configurations and/or approachesdescribed herein are exemplary in nature, and that these specificembodiments or examples are not to be considered in a limiting sense,because numerous variations are possible. The specific routines ormethods described herein may represent one or more of any number ofprocessing strategies. As such, various acts illustrated and/ordescribed may be performed in the sequence illustrated and/or described,in other sequences, in parallel, or omitted. Likewise, the order of theabove-described processes may be changed.

The subject matter of the present disclosure includes all novel andnonobvious combinations and subcombinations of the various processes,systems and configurations, and other features, functions, acts, and/orproperties disclosed herein, as well as any and all equivalents thereof.

The subject matter of the present disclosure is further described in thefollowing paragraphs. According to one aspect, a method of storing datafrom a whiteboard application executed on a computing system includingan interactive display device is provided. The method includes, storing,in a memory of the computing system, whiteboard data input to thewhiteboard application in response to user interaction with theinteractive display device, displaying a login selector on theinteractive display device, and upon detecting actuation of the loginselector; identifying the user based on credentials of the user; inresponse to identifying the user, (i) retrieving previews of storedwhiteboard files from a user account in a cloud-based storage systemcorresponding to the identity of the user, (ii) displaying the previewson the interactive display device, and (iii) uploading the whiteboarddata as a whiteboard file from the memory of the computing system to theuser account.

In this aspect, the method may further include displaying a logoutselector on the interactive display device; and upon detecting actuationof the logout selector, revoking access to the user account and removingthe previews of the stored whiteboard files from the interactive displaydevice.

In this aspect, identifying the user based on credentials of the usermay further comprise: prompting the user to input a username and apassword associated with a user account on a cloud-based storage system.

In this aspect, identifying the user based on credentials of the usermay further comprise: determining the identity of the user based on afacial recognition.

In this aspect, identifying the user based on credentials of the usermay further comprise: wirelessly detecting the credentials of the userstored in a linked portable device; and determining the identity of theuser based on the credentials.

In this aspect, the linked portable device may be one of a stylus,mobile computing device, and security token device.

In this aspect, the method may further include receiving a selectioninput of one of the previews via the interactive display device;retrieving the stored whiteboard file corresponding to the selectedpreview from the cloud-based storage system; and displaying the storedwhiteboard file on the interactive display device.

In this aspect, the method may further include displaying a second loginselector on the interactive display device; upon detecting actuation ofthe second login selector, identifying a second user based oncredentials of the second user; and in response to identifying thesecond user, uploading the whiteboard data from the memory of thecomputing system to a second user account in the cloud-based storagesystem, the second user account distinct from the first user account.

In this aspect, the method may further include detecting a privacykeyword via handwriting recognition on the interactive display device;assigning a privacy level to the whiteboard data based on the privacykeyword; and restricting access to the whiteboard data based on theprivacy level.

In this aspect, the whiteboard data may be in a data format specific tothe whiteboard application.

In this aspect, the uploaded whiteboard data may only include a selectedportion of data presented on the interactive touch sensitive displayassociated with the whiteboard application.

According to another aspect, a computing system is provided whichincludes an interactive touch sensitive display device; code stored inmemory executable by a processor to: store, in a memory of the computingsystem, whiteboard data input to the whiteboard application in directresponse to user interaction with the interactive touch sensitivedisplay device; display a login selector on the interactive touchsensitive display device; upon detecting actuation of the loginselector, identifying the user based on credentials of the user; and inresponse to identifying the user, (i) retrieve previews of storedwhiteboard files from the user account on the cloud-based storagesystem, (ii) display the previews on the interactive touch sensitivedisplay device, and (iii) upload the whiteboard data as a whiteboardfile from the memory of the computing system to the user account.

In this aspect, the whiteboard data may be in a data format specific tothe whiteboard application.

In this aspect, the whiteboard data may include at least one ofmodifiable ink input data, touch input data, and sticky-note dataassociated with a location or another element in the whiteboard data.

In this aspect, the computing system may further include code stored inmemory executable by a processor to; detect a privacy keyword viahandwriting recognition on the interactive touch sensitive displaydevice; assign a privacy level to the whiteboard data based on theprivacy keyword; and restrict access to the whiteboard data based on theprivacy level.

In this aspect, the credentials may be supplied by at least one of astylus, mobile computing device, and security token device via wirelesscommunication.

In this aspect, the whiteboard data may be uploaded in direct responseto identifying the user.

According to another aspect, a method of storing data from a whiteboardapplication executed on a computing system including an interactivetouch sensitive display device is provided. The method includes storing,in a memory of the computing system, whiteboard data input to thewhiteboard application in direct response to user interaction with theinteractive touch sensitive display device, the whiteboard data includesat least one of modifiable ink input data, touch input data, andsticky-note data associated with a location or another element in thewhiteboard data; displaying a login selector on the interactive touchsensitive display device; upon detecting actuation of the loginselector, identifying the user based on credentials of the user; and inresponse to identifying the user, (i) retrieving previews of storedwhiteboard files from the user account on the cloud-based storagesystem, (ii) displaying the previews on the interactive touch sensitivedisplay device, and (iii) uploading the whiteboard data as a whiteboardfile from the memory of the computing system to the user account.

In this aspect, the whiteboard data may be uploaded in direct responseto identifying the user.

In this aspect, the uploaded whiteboard data may only include a selectedportion of data presented on the interactive touch sensitive displayassociated with the whiteboard application.

1. A method of storing data from a whiteboard application executed on acomputing system including an interactive display device, the methodcomprising: associating whiteboard data with a first user, thewhiteboard data input to the whiteboard application responsive tointeraction of the first user with the interactive display device;detecting a privacy keyword inputted by the first user via handwritingrecognition on the interactive display device; assigning a privacy levelto the whiteboard data associated with the first user based on theprivacy keyword; detecting actuation of a first login selector by asecond user; determining credentials of the second user to identify thesecond user in response to detecting actuation of the first loginselector; determining that the second user is not authorized to accessthe whiteboard data associated with the first user based on the privacylevel and the credentials of the second user; and restricting the seconduser's access to the whiteboard data associated with the first user inresponse to determining that the second user is not authorized to accessthe whiteboard data.
 2. The method of claim 1, where the credentials ofthe second user include biometric data.
 3. The method of claim 2, wherethe biometric data includes facial image recognition data.
 4. The methodof claim 1, where restricting the second user's access to the whiteboarddata includes preventing display of a preview of the whiteboard dataassociated with the first user.
 5. The method of claim 4, wherepreventing display of the preview of the whiteboard data associated withthe first user includes preventing display of the preview when both thefirst user and the second user are logged into the whiteboardapplication.
 6. The method of claim 1, further comprising, subsequent toassigning the privacy level to the whiteboard data and prior todetecting actuation of the first login selector, detecting actuation ofa second login selector by the first user; determining credentials ofthe first user to identify the first user in response to detectingactuation of the second login selector; determining the first user isauthorized to access the whiteboard data based on the credentials of thefirst user and the privacy level of the whiteboard data; and in responseto determining the first user is authorized to access the whiteboarddata, (i) retrieving previews of stored whiteboard files from a firstuser account in a cloud-based storage system corresponding to theidentity of the first user, (ii) displaying the previews on theinteractive display device, and (iii) uploading the whiteboard data as awhiteboard file from the memory of the computing system to the useraccount.
 7. The method of claim 1, further comprising, subsequent toidentifying the second user, displaying a plurality of previews ofauthorized whiteboard data.
 8. The method of claim 1, where detectingthe privacy keyword includes detecting an ink input implemented via astylus or a digit of the first user interacting with the interactivedisplay device.
 9. The method of claim 1, further comprising displayinga warning message when the second user is restricted from accessing thewhiteboard data.
 10. A computing system comprising: an interactive touchsensitive display device; code stored in memory executable by aprocessor to: associate whiteboard data with a first user, thewhiteboard data input to the whiteboard application responsive tointeraction of the first user with the interactive display device;detect a privacy keyword inputted by the first user via handwritingrecognition on the interactive display device; assign a privacy level tothe whiteboard data associated with the first user based on the privacykeyword; detect actuation of a first login selector by a second user;identify the second user based on credentials of the second user inresponse to detecting actuation of the first login selector; determinethat the second user is not authorized to access the whiteboard dataassociated with the first user based on the privacy level and thecredentials of the second user; and restrict the second user's access tothe whiteboard data associated with the first user in response todetermining that the second user is not authorized to access thewhiteboard data.
 11. The computing system of claim 10, where thecredentials of the second user include biometric data.
 12. The computingsystem of claim 11, where the biometric data includes facial imagerecognition data.
 13. The computing system of claim 10, whererestricting the second user's access to the whiteboard data includespreventing display of a preview of the whiteboard data associated withthe first user.
 14. The computing system of claim 13, where preventingdisplay of the preview of the whiteboard data associated with the firstuser includes preventing display of the preview when both the first userand the second user are logged into the whiteboard application.
 15. Thecomputing system of claim 10, further comprising code stored in memoryexecutable by the processor to: subsequent to assigning the privacylevel to the whiteboard data and prior to detecting actuation of thefirst login selector, detect actuation of a second login selector by thefirst user; determine credentials of the first user to identify thefirst user in response to detecting actuation of the second loginselector; determine the first user is authorized to access thewhiteboard data based on the credentials of the first user and theprivacy level of the whiteboard data; and in response to determining thefirst user is authorized to access the whiteboard data, (i) retrievepreviews of stored whiteboard files from a first user account in acloud-based storage system corresponding to the identity of the firstuser, (ii) display the previews on the interactive display device, and(iii) upload the whiteboard data as a whiteboard file from the memory ofthe computing system to the user account.
 16. The computing system ofclaim 10, further comprising code stored in memory executable by theprocessor to, subsequent to identifying the second user, display aplurality of previews of authorized whiteboard data.
 17. The computingsystem of claim 10, where detecting of the privacy keyword includesdetecting an ink input implemented via a stylus or a digit of the firstuser interacting with the interactive display device.
 18. A method ofstoring data from a whiteboard application executed on a computingsystem including an interactive display device, the method comprising:associating whiteboard data with a first user, the whiteboard data inputto the whiteboard application responsive to interaction of the firstuser with the interactive display device; detecting a privacy keywordinputted by the first user via handwriting recognition on theinteractive display device; assigning a privacy level to the whiteboarddata associated with the first user based on the privacy keyword;detecting actuation of a first login selector by a second user;identifying the second user based on biometric data of the second userin response to detecting actuation of the first login selector;determining that the second user is not authorized to access thewhiteboard data associated with the first user based on the privacylevel and the biometric data of the second user; and restricting thesecond user's access to the whiteboard data associated with the firstuser in response to determining that the second user is not authorizedto access the whiteboard data.
 19. The method of claim 18, where thebiometric data includes facial image recognition data.
 20. The method ofclaim 18, further comprising, subsequent to assigning the privacy levelto the whiteboard data and prior to detecting actuation of the firstlogin selector, detecting actuation of a second login selector by thefirst user; determining credentials of the first user to identify thefirst user in response to detecting actuation of the second loginselector; determining the first user is authorized to access thewhiteboard data based on the credentials of the first user and theprivacy level of the whiteboard data; and in response to determining thefirst user is authorized to access the whiteboard data, (i) retrievingpreviews of stored whiteboard files from a first user account in acloud-based storage system corresponding to the identity of the firstuser, (ii) displaying the previews on the interactive display device,and (iii) uploading the whiteboard data as a whiteboard file from thememory of the computing system to the user account.